Relay communication method and relay communications apparatus and system

ABSTRACT

A relay communication method and a relay communications apparatus and system, for receiving, by a relay terminal, a first message sent by an access network device, where the first message includes configuration information of a first bearer; and configuring, by the relay terminal, an adaptation layer logical entity for the first bearer based on the first message, where the first bearer is a bearer between the relay terminal and the access network device, and the adaptation layer logical entity is used to distinguish between data of the relay terminal and data of a remote terminal or between data of different remote terminals.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/CN2017/079116, filed on Mar. 31, 2017, the disclosure of which ishereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present invention relates to the field of communicationstechnologies, and in particular, to a relay communication method and arelay communications apparatus and system.

BACKGROUND

With the emergence and update of a smartwatch, a smart band, and smartglasses, a wearable device has become increasingly popular. Anapplication based on the wearable device and a communications technologyfor the wearable device have also become research hotspots in a globalcommunications industry.

In a typical application scenario of the wearable device, the wearabledevice generally sets up a wireless connection to a cellular network(for example, a long term evolution (LTE) network) through forwardingperformed by a relay terminal (for example, a smartphone), andcommunicates with the cellular network. In this way, a user can directlytransmit data of various services to the network by using variousapplications (APP) on the wearable device. A communication manner inwhich the wearable device performs relay transmission by using the relayterminal is also referred to as user equipment (UE)-to-network relaytransmission.

To implement a relay function of the relay terminal, a layer 2 relayfunction is added to a communications protocol stack architecture of therelay terminal. The layer 2 relay function is located above a radio linkcontrol (RLC) layer (where the RLC layer is not included) and below aninternet protocol (IP) layer or a radio resource control (RRC) layer(where neither the IP layer nor the RRC layer is included). Currentcommunications protocol stack architectures of a terminal and an accessnetwork device do not include the relay function. Therefore, the accessnetwork device cannot configure the relay function of the relayterminal. As a result, the access network device does not support inconfiguring a relay bearer of the relay terminal using the relayfunction.

SUMMARY

To resolve the problem that the prior art does not support inconfiguring a relay bearer of a relay terminal using a relay function,embodiments of the present invention provide a relay communicationmethod and a relay communications apparatus and system.

According to a first aspect, an embodiment of the present inventionprovides a relay communication method. The method includes: receiving,by a relay terminal, a first message sent by an access network device,where the first message includes configuration information of a firstbearer; and configuring, by the relay terminal, an adaptation layerlogical entity for the first bearer based on the first message, wherethe first bearer is a bearer between the relay terminal and the accessnetwork device, and the adaptation layer logical entity is used todistinguish between data of the relay terminal and data of a remoteterminal or between data of different remote terminals.

In a possible implementation, the configuration information of the firstbearer includes a first bearer identifier and adaptation functionconfiguration information. The adaptation function configurationinformation includes an identifier of the remote terminal and/or abearer identifier of the remote terminal.

Further, the configuring, by the relay terminal, an adaptation layerlogical entity for the first bearer based on the first message mayinclude the following cases.

In a first case, the relay terminal has not set up the first bearer, andthe relay terminal newly sets up the first bearer based on the firstmessage. In this case, if existing bearers of the relay terminal do notinclude the first bearer, the relay terminal sets up the first bearer,and sets up the adaptation layer logical entity for the first bearerbased on the adaptation function configuration information.

In a second case, the relay terminal has set up the first bearer, andthe relay terminal configures the adaptation layer logical entity of thefirst bearer based on the adaptation function configuration information.Herein, the configuration may include setting up the adaptation layerlogical entity for the first bearer, or reconfiguring the adaptationlayer logical entity of the first bearer, or releasing the adaptationlayer logical entity of the first bearer.

In another possible implementation, the configuration information of thefirst bearer includes a first bearer identifier and bearer releaseindication information. The configuring, by the relay terminal, anadaptation layer logical entity for the first bearer based on the firstmessage means that the relay terminal has set up the first bearer, andthe relay terminal releases the first bearer based on the first message.Specifically, releasing the first bearer includes releasing a resourceof the first bearer. The resource of the first bearer includes theadaptation layer logical entity.

In still another possible implementation, the configuration informationof the first bearer includes a first bearer identifier and a bearertype. The bearer type is a relay bearer or a common bearer. The relaybearer is used to transmit the data of the remote terminal or is used totransmit the data of the remote terminal and the data of the relayterminal, and the common bearer is used to transmit the data of therelay terminal.

Further, the configuring, by the relay terminal, an adaptation layerlogical entity for the first bearer based on the first message mayinclude the following cases.

In a first case, the relay terminal has not set up the first bearer andthe bearer type in the first message is the relay bearer, and the relayterminal newly sets up the first bearer based on the first message. Inthis case, if existing bearers of the relay terminal do not include thefirst bearer, the relay terminal sets up the first bearer, and sets upthe adaptation layer logical entity for the first bearer.

In a second case, the relay terminal has set up the first bearer, andthe relay terminal configures the adaptation layer logical entity forthe first bearer based on the bearer type. Specifically, theconfiguration may include: when the first bearer in the existing bearersis the common bearer, and the bearer type is the relay bearer, settingup the adaptation layer logical entity for the first bearer, therebychanging the common bearer to the relay bearer; or when the first bearerin the existing bearers is the relay bearer, and the bearer type is thecommon bearer, releasing the adaptation layer logical entity of thefirst bearer, thereby changing the relay bearer to the common bearer.

According to a second aspect, an embodiment of the present inventionprovides a relay communication method. The method includes: determining,by an access network device, configuration information of a firstbearer, where the first bearer is a bearer between the access networkdevice and a relay terminal; and sending, by the access network device,a first message to the relay terminal, where the first message includesthe configuration information of the first bearer, the configurationinformation of the first bearer is used to instruct the relay terminalto configure an adaptation layer logical entity for the first bearer,and the adaptation layer logical entity is used to distinguish betweendata of the relay terminal and data of a remote terminal or between dataof different remote terminals.

In the first aspect and the second aspect, the access network deviceinstructs, by using the first message, the relay terminal to configurethe adaptation layer logical entity for the first bearer, therebysupporting in configuring a relay bearer of the relay terminal using anL2 relay protocol stack. There are a plurality of types of L2 relayprotocol stacks. All protocol stacks with a relay function above an RLClayer (where the RLC layer is not included) and below an IP layer or anRRC layer (where neither the IP layer nor the RRC layer is included)belong to the L2 relay protocol stack. Herein, configuring theadaptation layer logical entity for the first bearer includes settingup, modifying, or releasing the adaptation layer logical entity. Theadaptation layer logical entity is specifically used to determinewhether data is transmitted from/to the remote terminal or the relayterminal, or determine which bearer of the remote terminal the databelongs to, or distinguish between data transmitted from/to differentremote terminals.

In the first aspect and the second aspect, the first message may be anRRC connection reconfiguration message, an RRC connection setup message,or another grant message sent by the access network device to the relayterminal.

In the first aspect and the second aspect, the adaptation layer logicalentity may be an adaptation protocol entity or an adaptation function ofa PDCP entity. When the adaptation layer logical entity is theadaptation protocol entity, the adaptation function configurationinformation further includes an enabling indication or a disablingindication. The enabling indication is used to instruct the relayterminal to enable the adaptation function of the PDCP entity, and thedisabling indication is used to instruct the relay terminal to disablethe adaptation function of the PDCP entity.

According to a third aspect, an embodiment of the present inventionprovides a relay communication method. The method includes: generating aMAC PDU, where the MAC PDU includes a MAC CE, the MAC CE includes anidentifier of a remote terminal, and the MAC PDU carries data of asignaling radio bearer SRB0 of the remote terminal; and sending the MACPDU.

The relay communication method in the third aspect may be performed byan access network device or by the remote terminal. When the method isperformed by the access network device, the data of the SRB0 may be anRRC connection setup message. When the method is performed by the remoteterminal, the data of the SRB0 may be an RRC connection setup request.

According to a fourth aspect, an embodiment of the present inventionprovides a relay communication method. The method includes: receiving aMAC PDU, where the MAC PDU includes a medium access control controlelement MAC CE, the MAC CE includes an identifier of a remote terminal,and the MAC PDU carries data of a signaling radio bearer SRB0 of theremote terminal; obtaining the identifier of the remote terminal fromthe MAC CE of the MAC PDU; and sending the MAC PDU.

In the third aspect and the fourth aspect, the identifier of the remoteterminal is a local identifier of the remote terminal. The localidentifier is an identifier used by the access network device and therelay terminal to identify the remote terminal. During implementation,the local identifier may be allocated by the access network device orthe relay terminal.

According to a fifth aspect, an embodiment of the present inventionprovides a relay communications apparatus. The apparatus includes unitsconfigured to implement the method described in the first aspect, forexample, a receiving unit and a configuration unit.

According to a sixth aspect, an embodiment of the present inventionprovides a relay communications apparatus. The apparatus includes unitsconfigured to implement the method described in the second aspect, forexample, a generation unit and a sending unit.

According to a seventh aspect, an embodiment of the present inventionprovides a relay communications apparatus. The apparatus includes unitsconfigured to implement the method described in the third aspect, forexample, a generation unit and a sending unit.

According to an eighth aspect, an embodiment of the present inventionprovides a relay communications apparatus. The apparatus includes unitsconfigured to implement the method described in the fourth aspect, forexample, a receiving unit, an obtaining unit, and a sending unit.

According to a ninth aspect, an embodiment of the present inventionfurther provides a relay communications apparatus, applied to a relayterminal. The apparatus includes a memory and a processor connected tothe memory. The memory is configured to store a software program and amodule. When running or executing the software program and the modulestored in the memory, the processor may perform the method described inthe first aspect or the fourth aspect.

According to a tenth aspect, an embodiment of the present inventionfurther provides a relay communications apparatus, applied to an accessnetwork device. The apparatus includes a memory and a processorconnected to the memory. The memory is configured to store a softwareprogram and a module. When running or executing the software program andthe module stored in the memory, the processor may perform the methoddescribed in the second aspect or the third aspect.

According to an eleventh aspect, an embodiment of the present inventionfurther provides a computer readable medium, configured to store programcode to be executed by a terminal. The program code includes aninstruction used to perform the method described in the first aspect orthe fourth aspect.

According to a twelfth aspect, an embodiment of the present inventionfurther provides a computer readable medium, configured to store programcode to be executed by an access network device. The program codeincludes an instruction used to perform the method described in thesecond aspect or the third aspect.

According to a thirteenth aspect, an embodiment of the present inventionfurther provides a communications chip, applied to a mobilecommunications system device. The communications chip includes aprocessor, a memory, and a communications interface. The processor, thememory, and the communications interface are coupled by using a bus. Thememory is configured to store a program instruction. The processorexecutes the program instruction stored in the memory, so that thecommunications system device on which the communications chip isdisposed can perform the method provided in any one of the possibleimplementations of the first aspect, the second aspect, the thirdaspect, or the fourth aspect.

According to a fourteenth aspect, an embodiment of the present inventionfurther provides a relay communications system. The system includes anaccess network device, a relay terminal, and a remote terminal. Theaccess network device includes the relay communications apparatusprovided in the sixth aspect, and the relay terminal includes the relaycommunications apparatus provided in the fifth aspect. Alternatively,the access network device includes the relay communications apparatusprovided in the ninth aspect, and the relay terminal includes the relaycommunications apparatus provided in the tenth aspect.

According to a fifteenth aspect, an embodiment of the present inventionfurther provides a relay communications system. The system includes anaccess network device, a relay terminal, and a remote terminal. Theaccess network device and the remote terminal include the relaycommunications apparatus provided in the seventh aspect, and the relayterminal includes the relay communications apparatus provided in theeighth aspect.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic architectural diagram of a relay communicationssystem according to an embodiment of the present invention;

FIG. 2a is a schematic diagram of a wireless protocol stack used when aterminal communicates with an access network device;

FIG. 2b is a schematic diagram of a wireless protocol stack used when aremote terminal communicates with an access network device by using arelay terminal;

FIG. 3a is a flowchart of an existing process of setting up a bearerbetween a terminal and an access network device;

FIG. 3b is a flowchart of an existing process of modifying a bearerbetween a terminal and an access network device;

FIG. 3c is a flowchart of an existing process of releasing a bearerbetween a terminal and an access network device;

FIG. 4 is a schematic diagram a hardware structure of an access networkdevice according to an embodiment of the present invention;

FIG. 5 is a schematic diagram a hardware structure of a terminalaccording to an embodiment of the present invention;

FIG. 6 is a flowchart of a relay communication method according to anembodiment of the present invention;

FIG. 7 is a flowchart of another relay communication method according toan embodiment of the present invention;

FIG. 8 is a flowchart of still another relay communication methodaccording to an embodiment of the present invention;

FIG. 9 is a flowchart of still another relay communication methodaccording to an embodiment of the present invention;

FIG. 10 is a flowchart of still another relay communication methodaccording to an embodiment of the present invention;

FIG. 11 is a flowchart of still another relay communication methodaccording to an embodiment of the present invention;

FIG. 12 is a flowchart of still another relay communication methodaccording to an embodiment of the present invention;

FIG. 13a is a flowchart of still another relay communication methodaccording to an embodiment of the present invention;

FIG. 13b is a flowchart of still another relay communication methodaccording to an embodiment of the present invention;

FIG. 14 is a schematic diagram of a format of a MAC PDU according to anembodiment of the present invention;

FIG. 15 is a structural block diagram of a relay communicationsapparatus according to an embodiment of the present invention;

FIG. 16 is a structural block diagram of another relay communicationsapparatus according to an embodiment of the present invention;

FIG. 17 is a structural block diagram of another relay communicationsapparatus according to an embodiment of the present invention;

FIG. 18 is a structural block diagram of another relay communicationsapparatus according to an embodiment of the present invention; and

FIG. 19 is a structural diagram of a communications chip according to anembodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

A “module” mentioned in this specification is a program or aninstruction that is stored in a memory and that can implement somefunctions. A “unit” mentioned in this specification is a functionalstructure obtained through logic-based division. The “unit” may beimplemented by hardware only, or implemented by a combination ofsoftware and hardware.

FIG. 1 shows a relay communications system according to an embodiment ofthe present invention. The relay communications system 100 may be an LTEsystem, a 5G system, or a subsequent evolved system of the 5G system. Asshown in FIG. 1, the relay communications system includes an accessnetwork device 11, a relay terminal 12, and a remote terminal 13. Theremote terminal 13 communicates with the access network device 11 byusing the relay terminal 12.

Further, the relay terminal 12 is connected to the access network device11 by using a cellular network (including an uplink and a downlink). Theremote terminal 13 communicates with the relay terminal 12 through ashort-range communication link such as a sidelink, or by using Bluetoothor a wireless local area network WLAN.

In an uplink transmission direction, to be specific, in a direction fromthe remote terminal 13 to the access network device 11, when the remoteterminal 13 needs to send data, the remote terminal 13 first transmitsthe data to the relay terminal 12 through the sidelink, and then therelay terminal 12 sends the received data to the access network device11 through the cellular uplink. However, in a downlink transmissiondirection, to be specific, in a direction from the access network device11 to the remote terminal 13, the access network device 11 first sendsdata to the relay terminal 12 through the cellular downlink, and thenthe relay terminal 12 sends the data to the remote terminal 13 throughthe sidelink.

In the relay communications system shown in FIG. 1, the relay terminal12 may be a device such as a smartphone, a personal communicationsservice (PCS) phone, a cordless phone, a session initiation protocol(SIP) phone, a wireless local loop (WLL) station, or a personal digitalassistant (PDA). The terminal may also be referred to as a system, asubscriber unit, a subscriber station, a mobile station, a mobile, aremote station, an access point, a remote terminal, an access terminal,a user terminal, a user agent, or user equipment (UE). The remoteterminal 13 may be UE, an Internet of things device, or a wearabledevice such as a smart band, a smartwatch, or smart glasses.

The relay terminal 12 communicates with one or more access networkdevices 11 by using a radio access network (RAN).

The access network device 11 serves as a router between the relayterminal 12 and a remaining part of the access network. The remainingpart of the access network may include an Internet protocol (IP)network. The access network device 11 may further coordinate attributemanagement of an air interface. For example, the access network device11 may be a base transceiver station (BTS) in a global system for mobilecommunications (GSM) or a code division multiple access (CDMA) system,or may be a NodeB in wideband code division multiple access (WCDMA), ormay be an eNB in LTE. This is not limited in the present invention.

One relay terminal 12 can provide a relay function for one or moreremote terminals 13 (for example, in FIG. 1, one relay terminal 12provides a relay function for two remote terminals 13). When the relayterminal 12 provides the relay function, one radio bearer RB of therelay terminal 12 may be used to transmit data of an RB of one or moreremote terminals 13, and the data of the RB of the one or more remoteterminals 13 and data of the relay terminal may be transmitted on a Uuinterface (a radio interface between a base station and UE) by using oneRB of the relay terminal. When the RB of the relay terminal 12 is usedto transmit data of a plurality of RBs of the remote terminals 13, theplurality of RBs respectively belong to different remote terminals. Forexample, in FIG. 1, an RB1 and an RB2 respectively belong to differentremote terminals, but both data of the RB1 and data of the RB2 aretransmitted by using a bearer RB0 of the relay terminal.

In the embodiments of the present invention, the RB of the remoteterminal is an RB between the access network device and the remoteterminal, and the RB is a logical Uu bearer; and the RB of the relayterminal is an RB between the access network device and the relayterminal. In the present invention, RBs of the relay terminal areclassified into a common bearer and a relay bearer. The common bearer isan RB that carries only data of the relay terminal. The relay bearer isan RB used to carry data of the remote terminal or an RB that carriesboth data of the remote terminal and the data of the relay terminal. Asignaling flow of setting up the RB of the remote terminal may besimilar to a signaling flow of setting up the common bearer of the relayterminal. A message (for example, an RRC connection setup requestmessage, or an RRC connection setup message) used in a process ofsetting up the RB of the remote terminal may be forwarded by using therelay terminal.

FIG. 2a shows a protocol stack used when a relay terminal communicateswith an access network device (in other words, when communication isperformed based on a common bearer). For the common bearer, processingat a PDCP layer/an RLC layer/a MAC layer/a PHY layer is required.Setting up an RB means setting up a corresponding PDCP/RLC entity forthe RB based on a QoS parameter of the RB, setting up a correspondinglogical channel at a MAC layer, and configuring the logical channel.Modifying an RB means modifying a configuration of the correspondingPDCP/RLC entity and a configuration of the logical channel. Releasing anRB means releasing the corresponding PDCP/RLC entity and the logicalchannel.

FIG. 2b shows an L2 relay protocol stack used when a remote terminalcommunicates with an access network device by using a relay terminal (inother words, when communication is performed based on a relay bearer).The L2 relay protocol stack is the same as a UE-to-network relaywireless protocol stack defined in a 3rd generation partnership project(3GPP) standard for communication of a wearable device.

As shown in FIG. 2b , a packet data convergence protocol (PDCP) stackused by the Uu interface (referred to as a Uu PDCP below) exists betweenthe remote terminal and the access network device. The Uu PDCP stackincludes several radio bearers (English: Radio Bearer, RB for short)used for data transmission of the remote terminal. In addition, there isan adaptation layer below the Uu PDCP stack of the remote terminal. Theadaptation layer has at least one of the following functions: adding aheader to the data of the remote terminal, where the header includes anidentifier of the remote terminal; adding a radio bearer identifier RBIDof the remote terminal to the data; identifying data of the relayterminal and data of the remote terminal; identifying data of differentremote terminals; and identifying data of different radio bearers RBs ofthe remote terminal. The identifier of the remote terminal is used toenable a network side to distinguish between the data of differentremote terminals, and then send the data to different core networkgateways and servers for subsequent processing.

A PC5 interface wireless protocol stack is below the adaptation protocollayer. The PC5 interface wireless protocol stack includes a radio linkcontrol (RLC) layer (PC5), a medium access control protocol (MAC) layer(PC5), and a physical (PHY) layer (PC5). A PC5 interface is an interfaceused for direct data communication between the remote terminal and therelay terminal, and the PC5 interface is an air interface that isdefined in the 3GPP standard and that corresponds to an LTE D2Dtechnology. A sidelink corresponding to the PC5 interface is a “D2Dsidelink”.

Still referring to FIG. 2b , a packet data convergence protocol (PDCP)stack used by the Uu interface (referred to as a Uu PDCP below) existsbetween the relay terminal and the access network device. The Uu PDCPstack includes several radio bearers (RB) used for the data transmissionof the remote terminal. In addition, there is an adaptation layer belowthe Uu PDCP stack of the relay terminal. The adaptation layer has afunction of relaying the data of the remote terminal. Because the relayterminal also has data to be transmitted, the adaptation layer may beused to distinguish between the data of the relay terminal and the dataof the remote terminal or between the data of the different remoteterminals. Specifically, an adaptation layer logical entity is used todetermine whether the data is transmitted from/to the remote terminal orthe relay terminal, and determine which bearer of a specific remoteterminal the data belongs to. An RLC (Uu) layer, a MAC (Uu) layer, and aPHY (Uu) layer used by the Uu interface are below the adaptationprotocol layer.

FIG. 3a to FIG. 3c respectively show signaling flows of setting up,modifying (which may also be referred to as reconfiguring), andreleasing a common bearer. Processes of setting up, modifying, andreleasing the common bearer are respectively described below withreference to FIG. 3a to FIG. 3 c.

As shown in FIG. 3a , a procedure of setting up a common bearer includesthe following steps.

S301 a: After a terminal context is set up, a mobility management entity(MME) delivers an evolved radio access bearer (E-RAB) setup requestE-RAB SETUP REQUEST to an eNB to trigger setup of the common bearer.

S302 a: After receiving the request, the eNB sends an RRC connectionreconfiguration message to a terminal, where the RRC reconfigurationmessage includes a bearer setup modification list (drb-ToAddModList) ina dedicated radio resource configuration RadioResourceConfigDedicated.

Correspondingly, after receiving the RRC connection reconfigurationmessage, UE sets up a corresponding PDCP entity and configures acorresponding security parameter, sets up an RLC entity and configuresthe RLC entity, and sets up a logical channel at a MAC layer andconfigures the logical channel.

S303 a: After completing the configuration, the UE sends an RRCconnection reconfiguration complete message to the eNB.

S304 a: The eNB sends an E-RAB setup response E-RAB Setup Responsemessage to the MME.

As shown in FIG. 3b , a procedure of modifying a common bearer includesthe following steps.

S301 b: An MME delivers an E-RAB modify request E-RAB MODIFY REQUEST toan eNB to trigger a modification of the common bearer.

S302 b: After receiving the request, the eNB sends an RRC connectionreconfiguration message to a terminal, where the RRC reconfigurationmessage includes a bearer setup modification list (drb-ToAddModList) ina dedicated radio resource configuration RadioResourceConfigDedicated.

Correspondingly, after receiving the RRC connection reconfigurationmessage, UE reconfigures a corresponding PDCP entity, a correspondingRLC entity, and a corresponding logical channel.

S303 b: After completing the configuration, the UE sends an RRCconnection reconfiguration complete message to the eNB.

S304 b: The eNB sends an E-RAB modify response E-RAB Modify Responsemessage to the MME.

As shown in FIG. 3c , a procedure of releasing a common bearer includesthe following steps.

S301 c: An MME delivers an E-RAB release command E-RAB RELEASE COMMANDto an eNB to trigger release of the common bearer.

S302 c: After receiving the request, the eNB sends an RRC connectionreconfiguration message to a terminal, where the RRC reconfigurationmessage includes a bearer release list (drb-ToReleaseList) in adedicated radio resource configuration RadioResourceConfigDedicated.

Correspondingly, after receiving the RRC connection reconfigurationmessage, UE releases a corresponding PDCP entity, a corresponding RLCentity, and a corresponding logical channel.

S303 c: After completing the configuration, the UE sends an RRCconnection reconfiguration complete message to the eNB.

S304 c: The eNB sends an E-RAB release response E-RAB RELEASE Responsemessage to the MME.

In addition, the common bearer may be released together with a signalinglink.

It can be seen from the related procedures in FIG. 3a to FIG. 3c thatconfiguration of an adaptation layer logical entity is not involved inthe processes of setting up, modifying, and releasing the common bearer.Therefore, an existing protocol stack does not support setup,modification, and release of a relay bearer of a relay terminal using anL2 relay protocol stack. Therefore, in the present invention, adaptationfunction configuration information or a bearer type is added to the RRCconnection reconfiguration message (which is described in detail in thefollowing FIG. 6 to FIG. 14), to implement the configuration of theadaptation layer logical entity. The configuration herein includessetup, modification, and release.

The following describes a terminal and an access network device providedin the embodiments of the present invention with reference to specifichardware structures.

FIG. 4 shows a hardware structure of an access network device 400according to an embodiment of the present invention. The access networkdevice 400 may be an eNB. As shown in FIG. 4, the access network device400 includes a processor 41, a transceiver 42, and a memory 43.

The processor 41 includes one or more processing cores, and theprocessor 41 executes various function applications and informationprocessing by running a software program and a module.

The transceiver 42 includes a receiver Rx and a transmitter Tx. Thetransceiver 42 may be alternatively implemented as a communicationschip. The communications chip may include a receiving module, atransmission module, a modem module, and the like; and is configured to:modulate/demodulate information, and receive or send the information byusing a radio signal.

The transceiver 42, the memory 43, and the processor 41 are coupled byusing a bus. The memory 43 may be configured to store a software programand a module. The memory may store an operating system 44 and anapplication program module 45 of at least one function.

The application program module 45 includes at least a determining module451 and a sending module 452.

Optionally, the processor 41 is configured to execute modules in theapplication program module 45, to implement steps in FIG. 6 to FIG. 12that need to be performed by the access network device.

Alternatively, the application program module 45 includes at least ageneration module and a sending module. In this case, the processor 41is configured to execute the modules in the application program module45, to implement the steps in FIG. 13a and FIG. 13b that need to beperformed by the access network device.

In addition, the memory 43 is a computer readable storage medium, andmay be implemented by any type of volatile or non-volatile storagedevice or a combination thereof, such as a static random access memory(SRAM), an electrically erasable programmable read-only memory (EEPROM),an erasable programmable read-only memory (EPROM), a programmableread-only memory (PROM), a read-only memory (ROM), a magnetic memory, aflash memory, a magnetic disk, or an optical disc.

A person skilled in the art may understand that a structure of theaccess network device 400 shown in FIG. 4 does not constitute anylimitation on the access network device, and the access network devicemay include components more or fewer than those shown in the figure, acombination of some components, or components disposed differently.

FIG. 5 shows a hardware structure of a terminal 500 according to anembodiment of the present invention. The terminal 500 may be the relayterminal or the remote terminal described above, and may be specificallya mobile terminal such as a smartphone. As shown in FIG. 5, the terminal500 includes a processor 51, a transceiver 52, and a memory 53.

The processor 51 includes one or more processing cores, and theprocessor 51 executes various function applications and informationprocessing by running a software program and a module.

The transceiver 52 includes a receiver Rx and a transmitter Tx. Thetransceiver 52 may be alternatively implemented as a communicationschip. The communications chip may include a receiving module, atransmission module, a modem module, and the like; and is configured to:modulate/demodulate information, and receive or send the information byusing a radio signal.

The transceiver 52, the memory 53, and the processor 51 are coupled byusing a bus. The memory 53 may be configured to store a software programand a module. The memory may store an operating system 54 and anapplication program module 55 of at least one function.

The application program module 55 includes at least a receiving module551 and a configuration module 552.

Optionally, the processor 51 is configured to execute modules in theapplication program module 55, to implement steps in FIG. 6 to FIG. 12that need to be performed by the relay terminal.

Alternatively, the application program module 55 includes at least areceiving module, an obtaining module, and a sending module. In thiscase, the processor 51 is configured to execute the modules in theapplication program module 55, to implement the steps in FIG. 13a andFIG. 13b that need to be performed by the relay terminal.

Alternatively, the application program module 55 includes at least ageneration module and a sending module. In this case, the processor 51is configured to execute the modules in the application program module55, to implement the steps in FIG. 13a and FIG. 13b that need to beperformed by the remote terminal.

In addition, the memory 53 is a computer readable storage medium, andmay be implemented by any type of volatile or non-volatile storagedevice or a combination thereof, such as an SRAM, an EEPROM, an EPROM, aPROM, a ROM, a magnetic memory, a flash memory, a magnetic disk, or anoptical disc.

A person skilled in the art may understand that a structure of theterminal 500 shown in FIG. 5 does not constitute any limitation on theterminal, and the terminal 500 may include components more or fewer thanthose shown in the figure, a combination of some components, orcomponents disposed differently.

For ease of description, the following uses an example in which anaccess network device is a base station, a relay terminal is relay userequipment (UE), and a remote terminal is remote user equipment (UE) todescribe the embodiments of the present invention in detail.

FIG. 6 is a flowchart of a relay communication method according to anembodiment of the present invention. An example in which a relayterminal newly sets up a relay bearer based on adaptation functionconfiguration information is used to describe the relay communicationmethod in the present invention in detail. As shown in FIG. 6, themethod includes the following steps.

S601: A base station sends a first message to the relay terminal.

The first message may be an RRC connection reconfiguration message, andincludes configuration information of a first bearer. The configurationinformation of the first bearer includes a first bearer identifier andthe adaptation function configuration information. The first bearer is abearer between the base station and the relay terminal, namely, theforegoing RB of the relay terminal.

Optionally, the first bearer may be a data radio bearer (DRB), or may bea signaling radio bearer (SRB).

In an actual application, the first message includes a bearer setupmodification list, and the first bearer identifier is included in thebearer setup modification list. In an implementation, bearer setupmodification lists may be classified into a signaling radio bearer setupmodification list srb-ToAddModList and a data radio bearer setupmodification list drb-ToAddModList. The signaling radio bearer setupmodification list srb-ToAddModList includes a signaling radio beareridentifier. The data radio bearer setup modification listdrb-ToAddModList includes a data radio bearer identifier. The firstmessage includes at least one of the two lists. In anotherimplementation, bearer setup modification lists may not be classifiedinto a signaling radio bearer setup modification list and a data radiobearer setup modification list, and one list used in the first messageincludes both a signaling radio bearer identifier and a data radiobearer identifier. In these two implementations, the first bearer is anybearer that is in the bearer setup modification list and that has theadaptation function configuration information.

Certainly, the bearer setup modification list may further includeconfiguration information of a bearer that does not have adaptationfunction configuration information. The relay terminal may set up acommon bearer based on the configuration information of the bearer thatdoes not have the adaptation function configuration information.

Further, the first bearer identifier may be a specific value, and thevalue is used to uniquely represent a first bearer.

S602: The relay terminal receives the first message and obtains theconfiguration information of the first bearer in the first message.

S603: The relay terminal determines whether existing bearers of therelay terminal include the first bearer.

Specifically, the relay terminal determines whether a currentconfiguration of the relay terminal includes the first beareridentifier. If the current configuration of the relay terminal includesthe first bearer identifier, it indicates that the existing bearers ofthe relay terminal include the first bearer. If the currentconfiguration of the relay terminal does not include the first beareridentifier, it indicates that the existing bearers of the relay terminaldo not include the first bearer.

S604: If the existing bearers of the relay terminal do not include thefirst bearer, the relay terminal sets up the first bearer, and sets upan adaptation layer logical entity for the first bearer.

In a possible implementation, the adaptation layer logical entity may bea separate protocol entity, namely, an adaptation protocol entity(referred to as an adaptation layer entity in this application). In thisimplementation, the adaptation function configuration informationadaptation-Config is included in the first message as a separate part.Correspondingly, in this implementation, setting up the adaptation layerlogical entity for the first bearer includes setting up an adaptationprotocol entity based on the adaptation function configurationinformation. Optionally, the adaptation function configurationinformation includes at least one of an identifier of a remote terminaland a bearer identifier of the remote terminal. The identifier of theremote terminal may be a local identifier Local ID of the remoteterminal. The local identifier is used by a remote base station and therelay terminal to identify the remote terminal, and may be allocated bythe base station or the relay terminal. Further, setting up theadaptation protocol entity includes configuring a parameter for theadaptation entity based on the adaptation function configurationinformation adaptation-Config. The parameter may be a radio beareridentifier of the remote terminal and the identifier of the remoteterminal.

In another possible implementation, the adaptation layer logical entitymay be a function of a PDCP entity. In this implementation, theadaptation function configuration information is used as an integratedpart and included in PDCP configuration information carried in the firstmessage. In this implementation, setting up the adaptation layer logicalentity for the bearer corresponding to the first bearer identifier meansenabling an adaptation function of the PDCP entity. Correspondingly, inthis implementation, setting up the adaptation layer logical entity forthe first bearer includes setting up the PDCP entity and enabling theadaptation function of the PDCP entity. Optionally, the adaptationfunction configuration information may include at least one of thefollowing: the identifier of the remote terminal, the bearer identifierof the remote terminal, indication information used to indicate whetherthe adaptation function of the PDCP entity is enabled, indicationinformation used to instruct to delete the adaptation layer entity, andindication information used to instruct to set up the adaptation layerentity.

It is easy to learn that after setting up the first bearer, in additionto the adaptation layer logical entity set up for the first bearer, therelay terminal may further set up the PDCP entity, an RLC protocolentity, and a logical channel for the first bearer.

S605: The relay terminal sends a response message for the first messageto the base station.

Specifically, when the first message is the RRC connectionreconfiguration message, the response message for the first message isan RRC connection reconfiguration complete message.

FIG. 7 is a flowchart of a relay communication method according to anembodiment of the present invention. In the embodiment shown in FIG. 7,an example in which a relay terminal changes a common bearer to a relaybearer based on adaptation function configuration information is used todescribe the relay communication method in the present invention indetail. As shown in FIG. 7, the method includes the following steps.

S701: A base station sends a first message to the relay terminal.

For content of the first message, refer to S601. Details are notdescribed herein again.

S702: The relay terminal receives the first message and obtainsconfiguration information of a first bearer in the first message.

S703: The relay terminal determines whether existing bearers of therelay terminal include the first bearer.

An implementation of step S703 is the same as an implementation of stepS603, and a detailed description is omitted herein.

S704: If the existing bearers of the relay terminal include the firstbearer, and the existing first bearer does not have an adaptation layerlogical entity, the relay terminal sets up the adaptation layer logicalentity for the first bearer.

Specifically, whether the existing first bearer has the adaptation layerlogical entity may be determined in the following manner:

Whether a current configuration of the relay terminal includes theadaptation function configuration information in the first message isdetermined. If the current configuration of the relay terminal includesthe adaptation function configuration information in the first message,it indicates that the existing first bearer of the relay terminal hasthe adaptation layer logical entity; or if the current configuration ofthe relay terminal does not include the adaptation functionconfiguration information in the first message, it indicates that theexisting first bearer of the relay terminal does not have the adaptationlayer logical entity.

Alternatively, whether the existing first bearer has the adaptationlayer logical entity may be determined in the following manner:

Whether an adaptation function of a PDCP entity corresponding to thefirst bearer of the relay terminal is enabled is determined. If theadaptation function is enabled, it indicates that the existing firstbearer of the relay terminal has the adaptation layer logical entity; orif the adaptation function is disabled, it indicates that the existingfirst bearer of the relay terminal does not have the adaptation layerlogical entity.

In an implementation of setting up the adaptation layer logical entityfor the first bearer, the adaptation function configuration informationis used as an integrated part and included in PDCP configurationinformation carried in the first message. In this implementation,setting up an adaptation layer logical entity for a bearer correspondingto a first bearer identifier means enabling the adaptation function ofthe PDCP entity. Correspondingly, in this implementation, setting up theadaptation layer logical entity for the first bearer includes enablingthe adaptation function of the PDCP entity. Optionally, the adaptationfunction configuration information may include at least one of thefollowing: an identifier of a remote terminal, a bearer identifier ofthe remote terminal, indication information used to indicate whether theadaptation function of the PDCP entity is enabled, indicationinformation used to instruct to delete an adaptation layer entity, andindication information used to instruct to set up the adaptation layerentity. In a possible implementation, the adaptation layer logicalentity may be a separate protocol entity, namely, the adaptation layerentity. For details, refer to step S604. Details are not describedherein again.

For an implementation of content of the adaptation layer logical entity,refer to step S604. Details are not described herein again.

S705: The relay terminal sends a response message for the first messageto the base station.

FIG. 8 is a flowchart of a relay communication method according to anembodiment of the present invention. In the embodiment shown in FIG. 8,an example in which a relay terminal reconfigures a relay bearer basedon adaptation function configuration information is used to describe therelay communication method in the present invention in detail. As shownin FIG. 8, the method includes the following steps.

S801: A base station sends a first message to the relay terminal.

For content of the first message, refer to S601. Details are notdescribed herein again.

S802: The relay terminal receives the first message and obtainsconfiguration information of a first bearer in the first message.

S803: The relay terminal determines whether existing bearers of therelay terminal include the first bearer.

An implementation of step S803 is the same as an implementation of stepS603, and a detailed description is omitted herein.

S804: If the existing bearers of the relay terminal include the firstbearer, and the existing first bearer includes an adaptation layerlogical entity, the relay terminal reconfigures the adaptation layerlogical entity of the first bearer based on the adaptation functionconfiguration information in the first message.

For a manner of determining whether the existing first bearer includesthe adaptation layer logical entity, refer to step S704. For content ofthe adaptation layer logical entity, refer to step S604. Therefore,details are not described herein again.

In addition, reconfiguring the adaptation layer logical entity of thefirst bearer includes at least one of adding a new parameter andmodifying an original parameter. The parameter may be at least one of aradio bearer identifier of a remote terminal and an identifier of theremote terminal. For example, a relay bearer of the relay terminal hascarried data of the relay bearer and data of an RB of a first remoteterminal, and currently, the relay bearer further needs to carry data ofan RB of a second remote terminal. In this case, a radio beareridentifier of the second remote terminal and an identifier of the secondremote terminal are added to parameters of the adaptation layer logicalentity of the first bearer. The first remote terminal and the secondremote terminal are two different terminals. For another example, arelay bearer of the relay terminal has carried data of the relay bearerand data of an RB of a first remote terminal, and currently, the relaybearer needs to carry the data of the relay bearer and data of an RB ofa second remote terminal instead. In this case, an RB identifier of thefirst remote terminal and an identifier of the first remote terminal inparameters of the adaptation layer logical entity of the first bearerare replaced with a radio bearer identifier of a second remote terminaland an identifier of the second remote terminal. For another example, arelay bearer of the relay terminal has carried data of the relay bearer,data of an RB of a first remote terminal, and data of an RB of a secondremote terminal, and currently, the relay bearer does not carry the dataof the RB of the second remote terminal. In this case, a radio beareridentifier of the second remote terminal and an identifier of the secondremote terminal are deleted from parameters of the adaptation layerlogical entity of the first bearer.

S805: The relay terminal sends a response message for the first messageto the base station.

FIG. 9 is a flowchart of a relay communication method according to anembodiment of the present invention. In the embodiment shown in FIG. 9,an example in which a relay terminal changes a relay bearer of the relayterminal to a common bearer based on adaptation function configurationinformation is used to describe the relay communication method in thepresent invention in detail. As shown in FIG. 9, the method includes thefollowing steps.

S901: A base station sends a first message to the relay terminal.

For content of the first message, refer to S601. Details are notdescribed herein again.

S902: The relay terminal receives the first message and obtainsconfiguration information of a first bearer in the first message.

S903: The relay terminal determines whether existing bearers of therelay terminal include the first bearer.

An implementation of step S903 is the same as an implementation of stepS603, and a detailed description is omitted herein.

S904: If the existing bearers of the relay terminal include the firstbearer, and the existing first bearer includes an adaptation layerlogical entity, the relay terminal releases the adaptation layer logicalentity of the first bearer based on the adaptation functionconfiguration information in the first message.

In a possible implementation, the adaptation layer logical entity may bea separate protocol entity, namely, an adaptation protocol entity(referred to as an adaptation layer entity in this application).Correspondingly, in this implementation, if the adaptation functionconfiguration information includes indication information used toinstruct the relay terminal to release the adaptation layer entity, therelay terminal releases the adaptation layer logical entity of the firstbearer. Releasing the adaptation layer logical entity of the firstbearer includes releasing the adaptation layer entity.

In another possible implementation, the adaptation layer logical entitymay be a function of a PDCP entity. Correspondingly, in thisimplementation, if the adaptation function configuration informationincludes indication information used to indicate that an adaptationfunction of the PDCP entity is disabled, the relay terminal releases theadaptation layer logical entity of the first bearer. Releasing theadaptation layer logical entity of the first bearer includes disablingthe adaptation layer function of the PDCP entity.

S905: The relay terminal sends a response message for the first messageto the base station.

FIG. 10 is a flowchart of a relay communication method according to anembodiment of the present invention. In the embodiment shown in FIG. 10,an example in which a relay terminal releases a relay bearer based onconfiguration information of a first bearer is used to describe therelay communication method in the present invention in detail. As shownin FIG. 10, the method includes the following steps.

S1001: A base station sends a first message to the relay terminal.

The first message may be an RRC connection reconfiguration message, andincludes a first bearer identifier and bearer release indicationinformation. The first bearer is a bearer between the base station andthe relay terminal, namely, the foregoing RB of the relay terminal.Optionally, the first bearer may be a data radio bearer, or may be asignaling radio bearer.

In an actual application, the first message includes a bearer releaselist, and the first bearer identifier is included in the bearer releaselist. In an implementation, bearer release lists may be classified intoa signaling radio bearer release list srb-ToReleaseList and a data radiobearer release list drb-ToReleaseList. The signaling radio bearerrelease list srb-ToReleaseList includes a signaling radio beareridentifier. The data radio bearer release list drb-ToReleaseListincludes a data radio bearer identifier. The first message includes atleast one of the two lists. In another implementation, bearer releaselists may not be classified into a signaling radio bearer release listand a data radio bearer release list, and one list used in the firstmessage includes both a signaling radio bearer identifier and a dataradio bearer identifier. In these two implementations, the first beareris any bearer that is in the bearer release list and that has theadaptation function configuration information. Certainly, the bearersetup modification list may further include a bearer that does not havethe adaptation function configuration information.

Further, the first bearer identifier may be a specific value, and thevalue is used to uniquely represent a first bearer.

S1002: The relay terminal receives the first message and obtains theconfiguration information of the first bearer in the first message.

S1003: The relay terminal determines whether existing bearers of therelay terminal include the first bearer.

For a specific determining manner, refer to step S603. A detaileddescription is omitted herein.

S1004: If the existing bearers of the relay terminal include the firstbearer, the relay terminal releases a resource corresponding to thefirst bearer.

The resource corresponding to the first bearer includes an adaptationlayer logical entity.

S1005: The relay terminal sends a response message for the first messageto the base station.

FIG. 11 is a flowchart of a relay communication method according to anembodiment of the present invention. In the embodiment shown in FIG. 11,an example in which a relay terminal newly sets up a relay bearer basedon a bearer type is used to describe the relay communication method inthe present invention in detail. As shown in FIG. 11, the methodincludes the following steps.

S1101: A base station sends a first message to the relay terminal.

The first message may be an RRC connection reconfiguration message, andincludes configuration information of a first bearer. The configurationinformation of the first bearer includes a first bearer identifier and abearer type. Bearer types include a common bearer and a relay bearerdescribed above. In an actual application, the first message includes abearer setup modification list, and the first bearer identifier isincluded in the bearer setup modification list.

For detailed descriptions of the first bearer and the bearer setupmodification list, refer to step S601. A detailed description is omittedherein.

S1102: The relay terminal receives the first message and obtainsconfiguration information of a first bearer in the first message.

S1103: The relay terminal determines whether existing bearers of therelay terminal include the first bearer.

For a specific determining manner, refer to step S603. A detaileddescription is omitted herein.

S1104. If the existing bearers of the relay terminal do not include thefirst bearer, and a type of a bearer corresponding to a first beareridentifier is a relay bearer, the relay terminal sets up the firstbearer, and sets up an adaptation layer logical entity for the firstbearer.

If the configuration information of the first bearer further includesconfiguration information of the foregoing adaptation layer logicalentity, for a specific implementation of setting up the adaptation layerlogical entity for the first bearer, reference may be made to step S604.A detailed description is omitted herein.

S1105: The relay terminal sends a response message for the first messageto the base station.

FIG. 12 is a flowchart of a relay communication method according to anembodiment of the present invention. In the embodiment shown in FIG. 12,an example in which a relay terminal releases an adaptation layerlogical entity of an existing relay bearer or sets up an adaptationlayer logical entity for an existing relay bearer based on a bearer typeis used to describe the relay communication method in the presentinvention in detail. As shown in FIG. 12, the method includes thefollowing steps.

S1201: A base station sends a first message to the relay terminal.

For a description of the first message, refer to step S1101. A detaileddescription is omitted herein.

S1202: The relay terminal receives the first message and obtainsconfiguration information of a first bearer in the first message.

S1203: The relay terminal determines whether existing bearers of therelay terminal include the first bearer.

For a specific determining manner, refer to step S603. A detaileddescription is omitted herein.

S1204. If the existing bearers of the relay terminal include the firstbearer that is a common bearer, and a type of a bearer corresponding toa first bearer identifier in the first message is a relay bearer, therelay terminal sets up the adaptation layer logical entity for the firstbearer; or if the existing bearers of the relay terminal include thefirst bearer that is a relay bearer, and a type of a bearercorresponding to a first bearer identifier in the first message is acommon bearer, the relay terminal releases the adaptation layer logicalentity of the first bearer.

For a manner of setting up the adaptation layer logical entity, refer tostep S604. For a manner of releasing the adaptation layer logical entityof the first bearer, refer to step S904.

S1205: The relay terminal sends a response message for the first messageto the base station.

It should be noted that a condition for triggering a case in which thebase station sends an RRC connection reconfiguration message to therelay terminal is the same as the conditions shown in FIG. 3a to FIG.3C. Details are not described herein again.

It should be noted that, in this embodiment of the present invention, anexample in which the first message is the RRC connection reconfigurationmessage is used for description. The first message may also beimplemented in a form of another message, such as an RRC connectionsetup message or another grant message sent by the base station to therelay terminal.

FIG. 13a is a flowchart of another relay communication method accordingto an embodiment of the present invention. Referring to FIG. 13a , themethod includes the following steps.

S1301 a: An access network device generates a medium access control(MAC) protocol data unit (PDU) PDU.

The MAC PDU carries SRB0 data sent to the remote terminal. The SRB0 is asignaling radio bearer, and is generally used to transmit signaling ofsetting up or resetting up an RRC connection between UE and a basestation. For example, an RRC connection request message sent by the UEto the base station, an RRC connection setup message returned by thebase station to the UE, and the like are all transmitted by using theSRB0. The SRB0 data in this step may be the RRC connection setupmessage.

FIG. 14 is a schematic diagram of a format of a MAC PDU according to anembodiment of the present invention. Referring to FIG. 14, the MAC PDUincludes a MAC control element (CE) specifically used to distinguishbetween data of a relay terminal and data of the remote terminal, ordistinguish between data of different remote terminals. The MAC CEincludes an identifier of the remote terminal or indication information.The indication information is used to indicate whether the data is thedata of the relay terminal or the data of the remote terminal. Theidentifier of the remote terminal may be an identifier used by the basestation and the relay terminal to identify the remote terminal, forexample, a local ID.

S1302 a: The access network device sends the MAC PDU to a relayterminal.

Specifically, the access network device learns of, based on contextinformation that is of the relay terminal and that is stored in theaccess network device or context information of the remote terminal, aspecific terminal used as a relay of the remote terminal, and sends theMAC PDU to a relay terminal corresponding to the remote terminal.

S1303 a: The relay terminal receives the MAC PDU sent by the accessnetwork device and obtains an identifier of a remote terminal from theMAC CE.

S1304 a: The relay terminal sends the MAC PDU to the remote terminal towhich the identifier of the remote terminal belongs.

FIG. 13b is a flowchart of another relay communication method accordingto an embodiment of the present invention. Referring to FIG. 13b , themethod includes the following steps.

S1301 b: A remote terminal generates a MAC PDU.

The MAC PDU carries SRB0 data sent to a base station, for example, anRRC connection request message sent to the base station.

S1302 b: The remote terminal sends the MAC PDU to a relay terminal.

S1303 b: The relay terminal receives the MAC PDU sent by the remoteterminal and obtains an identifier of the remote terminal from a MAC CE.

S1304 b: The relay terminal sends the MAC PDU to the access networkdevice by using a relay bearer corresponding to the identifier of theremote terminal.

In the embodiments shown in FIG. 13a and FIG. 13b , because no PDCPentity and no actual RLC entity correspond to the SRB0, an adaptationfunction of the data of the SRB0 is implemented at a MAC layer. In otherwords, at the MAC layer, data of the relay terminal is distinguishedfrom data of the remote terminal, or data of different remote terminalsis distinguished from each other.

FIG. 15 is a block diagram of a relay communications apparatus accordingto an embodiment of the present invention. The relay communicationsapparatus may be implemented as all or a part of a relay terminal byusing a dedicated hardware circuit or a combination of software andhardware. The relay communications apparatus includes a receiving unit1501 and a configuration unit 1502. The receiving unit 1501 isconfigured to receive a first message sent by an access network device.The configuration unit 1502 is configured to configure an adaptationlayer logical entity for a first bearer based on the first messagereceived by the receiving unit 1501.

Optionally, the first message may be an RRC connection reconfigurationmessage, an RRC connection setup message, another grant message sent bya base station to the relay terminal, or the like.

In an implementation, configuration information of the first bearerincludes a first bearer identifier and adaptation function configurationinformation.

Further, the configuration unit 1502 is configured to: when existingbearers of the relay terminal do not include the first bearer, set upthe first bearer, and set up the adaptation layer logical entity for thefirst bearer based on the adaptation function configuration information;or the configuration unit 1502 is configured to: when existing bearersof the relay terminal include the first bearer, configure the adaptationlayer logical entity for the first bearer based on the adaptationfunction configuration information.

Still further, when the existing bearers of the relay terminal includethe first bearer, the configuration unit 1502 is specifically configuredto set up the adaptation layer logical entity for the first bearer; orreconfigure the adaptation layer logical entity of the first bearer; orrelease the adaptation layer logical entity of the first bearer.

In another implementation, the configuration information of the firstbearer includes a first bearer identifier and bearer release indicationinformation.

Correspondingly, the configuration unit 1502 is configured to release aresource of the first bearer, where the resource of the first bearerincludes the adaptation layer logical entity.

In still another implementation, the configuration information of thefirst bearer includes a first bearer identifier and a bearer type. Thebearer type is a relay bearer or a common bearer. The relay bearer isused to transmit data of a remote terminal or is used to transmit dataof a remote terminal and data of the relay terminal, and the commonbearer is used to transmit data of the relay terminal.

In this implementation, the configuration unit 1502 is configured to:when the existing bearers of the relay terminal do not include the firstbearer, and the bearer type is the relay bearer, set up the first bearerbased on the bearer type, and set up the adaptation layer logical entityfor the first bearer; or the configuration unit 1502 is configured to:when the existing bearers of the relay terminal include the firstbearer, configure the adaptation layer logical entity for the firstbearer based on the bearer type.

Still further, the configuration unit 1502 is specifically configuredto: when the first bearer in the existing bearers is the common bearerand the bearer type is the relay bearer, set up the adaptation layerlogical entity for the first bearer; or when the first bearer in theexisting bearers is the relay bearer and the bearer type is the commonbearer, release the adaptation layer logical entity of the first bearer.

Optionally, the adaptation layer logical entity is an adaptationprotocol entity or an adaptation function of a PDCP entity.

When the adaptation layer logical entity is the adaptation function ofthe PDCP entity, the adaptation function configuration information mayfurther include indication information used to instruct the relayterminal to enable or disable the adaptation function of the PDCPentity.

For related details, refer to the method embodiments of FIG. 6 to FIG.12.

It should be noted that the foregoing configuration unit 1502 may beimplemented by a processor or by a processor executing a programinstruction in a memory. The foregoing receiving unit 1501 may beimplemented by a receiver Rx or by the processor in cooperation with areceiver.

FIG. 16 is a block diagram of a relay communications apparatus accordingto an embodiment of the present invention. The relay communicationsapparatus may be implemented as all or a part of an access networkdevice by using a dedicated hardware circuit or a combination ofsoftware and hardware. The relay communications apparatus includes adetermining unit 1601 and a sending unit 1602. The determining unit 1601is configured to determine configuration information of a first bearer.The sending unit 1602 is configured to send a first message to a relayterminal, where the first message includes the configuration informationof the first bearer that is determined by the determining unit 1601.

In still another implementation, the configuration information of thefirst bearer includes a first bearer identifier and a bearer type. Thebearer type is a relay bearer or a common bearer. The relay bearer isused to transmit data of a remote terminal or is used to transmit dataof a remote terminal and data of the relay terminal, and the commonbearer is used to transmit data of the relay terminal. In anotherimplementation, the configuration information of the first bearerincludes a first bearer identifier and adaptation function configurationinformation. In another implementation, the configuration information ofthe first bearer includes a first bearer identifier and bearer releaseindication information.

Optionally, the adaptation function configuration information includesat least one of an identifier of the remote terminal and a beareridentifier of the remote terminal.

Optionally, an adaptation layer logical entity is an adaptation protocolentity or an adaptation function of a PDCP entity.

When the adaptation layer logical entity is the adaptation function ofthe PDCP entity, the adaptation function configuration informationfurther includes indication information used to instruct the relayterminal to enable or disable the adaptation function of the PDCPentity.

For related details, refer to the method embodiments of FIG. 6 to FIG.12.

It should be noted that the foregoing determining unit 1601 may beimplemented by a processor or by a processor executing a programinstruction in a memory. The foregoing sending unit 1602 may beimplemented by a transmitter or by the processor in cooperation with atransmitter.

FIG. 17 is a block diagram of a relay communications apparatus accordingto an embodiment of the present invention. The relay communicationsapparatus may be implemented as all or a part of a relay terminal byusing a dedicated hardware circuit or a combination of software andhardware. The relay communications apparatus includes a receiving unit1701, an obtaining unit 1702, and a sending unit 1703. The receivingunit is configured to receive a MAC PDU, where the MAC PDU includes amedium access control control element MAC CE, the MAC CE includes anidentifier of a remote terminal, and the MAC PDU carries data of asignaling radio bearer SRB0 of the remote terminal. The obtaining unit1702 is configured to obtain the identifier of the remote terminal fromthe MAC CE of the MAC PDU received by the receiving unit 1701. Thesending unit 1703 is configured to send the MAC PDU received by thereceiving unit 1701.

For related details, refer to the method embodiments of FIG. 13a , FIG.13b , and FIG. 14.

It should be noted that the foregoing obtaining unit 1702 may beimplemented by a processor or by a processor executing a programinstruction in a memory; the foregoing receiving unit 1701 may beimplemented by a receiver or by the processor in cooperation with areceiver; and the foregoing sending unit 1703 may be implemented by atransmitter or by the processor in cooperation with a transmitter.

FIG. 18 is a block diagram of a relay communications apparatus accordingto an embodiment of the present invention. The relay communicationsapparatus may be implemented as all or a part of an access networkdevice or a remote terminal by using a dedicated hardware circuit or acombination of software and hardware. The relay communications apparatusincludes a generation unit 1801 and a sending unit 1802. The generationunit 1801 is configured to generate a medium access control protocoldata unit MAC PDU, where the MAC PDU includes a medium access controlcontrol element MAC CE, the MAC CE includes an identifier of the remoteterminal, and the MAC PDU carries data of a signaling radio bearer SRB0of the remote terminal. The sending unit 1802 is configured to send theMAC PDU generated by the generation unit 1801 to a relay terminal.

The identifier of the remote terminal may be an identifier used by theaccess network device and the relay terminal to identify the remoteterminal, such as a local identifier.

For related details, refer to the method embodiments of FIG. 13a , FIG.13b , and FIG. 14.

It should be noted that the foregoing generation unit 1801 may beimplemented by a processor or by a processor executing a programinstruction in a memory. The foregoing sending unit 1802 may beimplemented by a transmitter or by the processor in cooperation with thetransmitter.

FIG. 19 is a schematic structural diagram of a communications chipaccording to an embodiment of the present invention. The communicationschip is applied to a mobile communications system device such as theforegoing access network device or the foregoing terminal. Thecommunications chip includes a processor 1910, a memory 1920, and acommunications interface 1930. The processor 1910 is connected to boththe memory 1920 and the communications interface 1930 by using a bus.

The communications interface 1930 is configured to implementcommunication with another communications device.

The processor 1910 includes one or more processing cores. The processor1910 runs an operating system or an application program module.

Optionally, the memory 1920 may store an operating system 1922 and anapplication program module 1924 required by at least one function.Optionally, the application program module 1924 includes a receivingmodule 1924 a, a processing module 1924 b, and a sending module 1924 c.The receiving module 1924 a is configured to implement steps related toreceiving. The processing module 1924 b is configured to implement stepsrelated to calculation or processing. The sending module 1924 c isconfigured to implement steps related to sending.

In addition, the memory 1920 may be implemented by any type of volatileor non-volatile storage device or a combination thereof, such as anSRAM, an EEPROM, an EPROM, a PROM, a ROM, a magnetic memory, a flashmemory, a magnetic disk, or an optical disc.

A person skilled in the art may understand that a structure shown inFIG. 19 does not constitute any limitation on the foregoingcommunications chip, and the communications chip may include componentsmore or fewer than those shown in the figure, a combination of somecomponents, or components disposed differently.

The foregoing descriptions are merely optional embodiments of thepresent invention, but are not intended to limit the present invention.Any modification, equivalent replacement, or improvement made withoutdeparting from the spirit and principle of present invention should fallwithin the protection scope of the present invention.

What is claimed is:
 1. A relay communication method, comprising:receiving, by a relay terminal, a first message sent by an accessnetwork device, wherein the first message comprises configurationinformation of a first bearer; and configuring, by the relay terminal,an adaptation layer logical entity for the first bearer based on thefirst message, wherein the first bearer is a bearer between the relayterminal and the access network device, and the adaptation layer logicalentity is used to distinguish between data of the relay terminal anddata of a remote terminal or between data of different remote terminals.2. The method according to claim 1, wherein the configurationinformation of the first bearer comprises a first bearer identifier andadaptation function configuration information.
 3. The method accordingto claim 2, wherein the configuring, by the relay terminal, of theadaptation layer logical entity for the first bearer based on the firstmessage comprises: if existing bearers of the relay terminal do notcomprise the first bearer, setting up, by the relay terminal, the firstbearer, and setting up the adaptation layer logical entity for the firstbearer based on the adaptation function configuration information; or ifexisting bearers of the relay terminal comprise the first bearer,configuring, by the relay terminal, the adaptation layer logical entityof the first bearer based on the adaptation function configurationinformation.
 4. The method according to claim 3, wherein theconfiguring, by the relay terminal, of the adaptation layer logicalentity of the first bearer based on the adaptation functionconfiguration information comprises: setting up the adaptation layerlogical entity for the first bearer; or reconfiguring the adaptationlayer logical entity of the first bearer; or releasing the adaptationlayer logical entity of the first bearer.
 5. The method according toclaim 2, wherein the adaptation function configuration informationcomprises at least one of an identifier of a remote terminal and abearer identifier of the remote terminal.
 6. The method according toclaim 1, wherein the configuration information of the first bearercomprises a first bearer identifier and bearer release indicationinformation.
 7. The method according to claim 6, wherein theconfiguring, by the relay terminal, of the adaptation layer logicalentity for the first bearer based on the first message comprises:releasing, by the relay terminal, a resource of the first bearer,wherein the resource of the first bearer comprises the adaptation layerlogical entity.
 8. The method according to claim 1, wherein theconfiguration information of the first bearer comprises a first beareridentifier and a bearer type, the bearer type is a relay bearer or acommon bearer, the relay bearer is used to transmit the data of theremote terminal or is used to transmit the data of the remote terminaland the data of the relay terminal, and the common bearer is used totransmit the data of the relay terminal.
 9. An apparatus, comprising: astorage medium including executable instructions; and a processor,wherein the executable instructions, when executed by the processor,cause the apparatus to: receive a first message sent by an accessnetwork device, wherein the first message comprises configurationinformation of a first bearer; and configure an adaptation layer logicalentity for the first bearer based on the first message, wherein thefirst bearer is a bearer between a relay terminal and the access networkdevice, and the adaptation layer logical entity is used to distinguishbetween data of the relay terminal and data of a remote terminal orbetween data of different remote terminals.
 10. The apparatus accordingto claim 9, wherein the configuration information of the first bearercomprises a first bearer identifier and adaptation functionconfiguration information.
 11. The apparatus according to claim 10,wherein the executable instructions, when executed by the processor,further cause the apparatus to: if existing bearers of the relayterminal do not comprise the first bearer, set up the first bearer, andset up the adaptation layer logical entity for the first bearer based onthe adaptation function configuration information; or if existingbearers of the relay terminal comprise the first bearer, configure theadaptation layer logical entity of the first bearer based on theadaptation function configuration information.
 12. The apparatusaccording to claim 11, wherein the executable instructions, whenexecuted by the processor, further cause the apparatus to: set up theadaptation layer logical entity for the first bearer; or reconfigure theadaptation layer logical entity of the first bearer; or release theadaptation layer logical entity of the first bearer.
 13. The apparatusaccording to claim 10, wherein the adaptation function configurationinformation comprises at least one of an identifier of a remote terminaland a bearer identifier of the remote terminal.
 14. The apparatusaccording to claim 9, wherein the configuration information of the firstbearer comprises a first bearer identifier and bearer release indicationinformation.
 15. The apparatus according to claim 14, wherein theexecutable instructions, when executed by the processor, further causethe apparatus to: release a resource of the first bearer, wherein theresource of the first bearer comprises the adaptation layer logicalentity.
 16. The apparatus according to claim 9, wherein theconfiguration information of the first bearer comprises a first beareridentifier and a bearer type, the bearer type is a relay bearer or acommon bearer, the relay bearer is used to transmit the data of theremote terminal or is used to transmit the data of the remote terminaland the data of the relay terminal, and the common bearer is used totransmit the data of the relay terminal.
 17. An apparatus, comprising: astorage medium including executable instructions; and a processor,wherein the executable instructions, when executed by the processor,cause the apparatus to: determine configuration information of a firstbearer, wherein the first bearer is a bearer between the access networkdevice and a relay terminal; and send a first message to the relayterminal, wherein the first message comprises the configurationinformation of the first bearer, the configuration information of thefirst bearer is used to instruct the relay terminal to configure anadaptation layer logical entity for the first bearer, and the adaptationlayer logical entity is used to distinguish between data of the relayterminal and data of a remote terminal or between data of differentremote terminals.
 18. The apparatus according to claim 17, wherein theconfiguration information of the first bearer comprises a first beareridentifier and a bearer type, the bearer type is a relay bearer or acommon bearer, the relay bearer is used to transmit the data of theremote terminal or is used to transmit the data of the remote terminaland the data of the relay terminal, and the common bearer is used totransmit the data of the relay terminal; or the configurationinformation of the first bearer comprises a first bearer identifier andadaptation function configuration information; or the configurationinformation of the first bearer comprises a first bearer identifier andbearer release indication information.
 19. The apparatus according toclaim 18, wherein the adaptation function configuration informationcomprises at least one of an identifier of the remote terminal and abearer identifier of the remote terminal.
 20. The apparatus according toclaim 18, wherein the adaptation layer logical entity is an adaptationprotocol entity or an adaptation function of a PDCP entity.